Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d85d343f3fd4ecc3a074a598c8d9ceb78fe58e9add6d9b61e79bc95df8d36086

Tx prefix hash: a717a44f9d04bb324401fece85fdbdcceaee59a99a6b1011fa77d036d62243b1
Tx public key: cd561e6ea9bf31305320b528416a564321ab1b22f85b6b60cc055f1d483758dc
Timestamp: 1742226199 Timestamp [UTC]: 2025-03-17 15:43:19 Age [y:d:h:m:s]: 01:242:15:07:39
Block: 1241366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437348 RingCT/type: yes/0
Extra: 01cd561e6ea9bf31305320b528416a564321ab1b22f85b6b60cc055f1d483758dc02110000000f007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7811ac0950748b6807ae5b316f346ce457804751e93a6ea13905bdce460ba27d 0.000600000000 1728339 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1241376, "vin": [ { "gen": { "height": 1241366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7811ac0950748b6807ae5b316f346ce457804751e93a6ea13905bdce460ba27d" } } ], "extra": [ 1, 205, 86, 30, 110, 169, 191, 49, 48, 83, 32, 181, 40, 65, 106, 86, 67, 33, 171, 27, 34, 248, 91, 107, 96, 204, 5, 95, 29, 72, 55, 88, 220, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: