Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cda1f4e33d284a42ecf5f504cfcb646b0cd250a5acc40830d8524aaa0d6c679

Tx prefix hash: ca1b2a0c94740f967ce03d4a0fcb6ce5916347cea6e88e4147e9700570452bbf
Tx public key: 1f7b8be9501ab401700074ca007ff54302d640c600386dbf63621b0c1b2c5b7c
Timestamp: 1773035092 Timestamp [UTC]: 2026-03-09 05:44:52 Age [y:d:h:m:s]: 00:018:15:15:57
Block: 1493864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13321 RingCT/type: yes/0
Extra: 011f7b8be9501ab401700074ca007ff54302d640c600386dbf63621b0c1b2c5b7c02110000000ae4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 892e45ddd88d9ce650699e3a36722b846d3bd419e6fbd2be9a6de244c6320074 0.000600000000 1983428 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": 1493874, "vin": [ { "gen": { "height": 1493864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "892e45ddd88d9ce650699e3a36722b846d3bd419e6fbd2be9a6de244c6320074" } } ], "extra": [ 1, 31, 123, 139, 233, 80, 26, 180, 1, 112, 0, 116, 202, 0, 127, 245, 67, 2, 214, 64, 198, 0, 56, 109, 191, 99, 98, 27, 12, 27, 44, 91, 124, 2, 17, 0, 0, 0, 10, 228, 245, 25, 63, 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) | dinastycoin version: tesla-369