Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1321b0dbd2201a450522fb666b4eb4767ad6bbcbc19ca157f08600c1b6fa8a

Tx prefix hash: a8f78dacfccd9e8d011e467b73b42bf7e60c19e48d47a7d28d6727934327b3eb
Tx public key: 214cc12257ab0bacd4f8f517554e41950a11c3a9ca22bfb7be87115f2b665f72
Timestamp: 1767902434 Timestamp [UTC]: 2026-01-08 20:00:34 Age [y:d:h:m:s]: 00:315:23:49:51
Block: 1451563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231344 RingCT/type: yes/0
Extra: 01214cc12257ab0bacd4f8f517554e41950a11c3a9ca22bfb7be87115f2b665f7202110000000349d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2eee5ebc641c1c2c4a596b2e32801826102bcde8504e2beb274bb677b8b523cd 0.000600000000 1940575 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": 1451573, "vin": [ { "gen": { "height": 1451563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eee5ebc641c1c2c4a596b2e32801826102bcde8504e2beb274bb677b8b523cd" } } ], "extra": [ 1, 33, 76, 193, 34, 87, 171, 11, 172, 212, 248, 245, 23, 85, 78, 65, 149, 10, 17, 195, 169, 202, 34, 191, 183, 190, 135, 17, 95, 43, 102, 95, 114, 2, 17, 0, 0, 0, 3, 73, 215, 62, 152, 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: