Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cb726a31da545141d2571c80ed0b8549cbf919c4a2bdc3f7f993d1d2fa35649

Tx prefix hash: 1b1bee03f242e3150c820b1ac2fcfb3397d54d83bee3a0a7f4b44fdb1cf27663
Tx public key: 9df54db8cd09a87a65b5bda9978f83b5936af8ba00c0bf83e9470551659d416e
Timestamp: 1772590994 Timestamp [UTC]: 2026-03-04 02:23:14 Age [y:d:h:m:s]: 00:261:20:55:12
Block: 1490198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192803 RingCT/type: yes/0
Extra: 019df54db8cd09a87a65b5bda9978f83b5936af8ba00c0bf83e9470551659d416e021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 17d5df032ecc9a08a415686ada7f998577718cb5a7161b0a6039c6f37d9692ff 0.000600000000 1979698 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": 1490208, "vin": [ { "gen": { "height": 1490198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d5df032ecc9a08a415686ada7f998577718cb5a7161b0a6039c6f37d9692ff" } } ], "extra": [ 1, 157, 245, 77, 184, 205, 9, 168, 122, 101, 181, 189, 169, 151, 143, 131, 181, 147, 106, 248, 186, 0, 192, 191, 131, 233, 71, 5, 81, 101, 157, 65, 110, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: