Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 671c61a219dafa71ba8a265b3a181c16cfa899d00f52522a9ecda23950d551da

Tx prefix hash: d912dfde088d7aad54002fe92496b2fcca1916736c16030e5af71888c69de8ba
Tx public key: e1e8da36bb4f5dfbffa3ec70e7b1d93c144a912bbb5aebb57987ad62d47a06a7
Timestamp: 1750959460 Timestamp [UTC]: 2025-06-26 17:37:40 Age [y:d:h:m:s]: 00:318:15:15:42
Block: 1313327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218202 RingCT/type: yes/0
Extra: 01e1e8da36bb4f5dfbffa3ec70e7b1d93c144a912bbb5aebb57987ad62d47a06a702110000000643846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 746caedaa291f3c9386bb76da227ff8d4bf10b340ee0d93a1d44c0ae30f39012 0.000600000000 1800966 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": 1313337, "vin": [ { "gen": { "height": 1313327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "746caedaa291f3c9386bb76da227ff8d4bf10b340ee0d93a1d44c0ae30f39012" } } ], "extra": [ 1, 225, 232, 218, 54, 187, 79, 93, 251, 255, 163, 236, 112, 231, 177, 217, 60, 20, 74, 145, 43, 187, 90, 235, 181, 121, 135, 173, 98, 212, 122, 6, 167, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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: