Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 521aec287be01bf58afc81811732bf8e9d08e494b232828a5576fcc6b4e0f28f

Tx prefix hash: 017217db6113caf48beae3426b82e903449211d1fef5853c432b487b0b0d87b0
Tx public key: cf1e330368bfec7134f7527d854fdc863bd1e8c408ac7af7f5f15d562b52e64f
Timestamp: 1769584335 Timestamp [UTC]: 2026-01-28 07:12:15 Age [y:d:h:m:s]: 00:106:02:11:56
Block: 1465308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68194 RingCT/type: yes/0
Extra: 01cf1e330368bfec7134f7527d854fdc863bd1e8c408ac7af7f5f15d562b52e64f02110000000149d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ec1ab1798c40962f79e50256520d26bf2bdb4d26f4394c301dcaede220b08eb3 0.000600000000 1954534 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": 1465318, "vin": [ { "gen": { "height": 1465308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec1ab1798c40962f79e50256520d26bf2bdb4d26f4394c301dcaede220b08eb3" } } ], "extra": [ 1, 207, 30, 51, 3, 104, 191, 236, 113, 52, 247, 82, 125, 133, 79, 220, 134, 59, 209, 232, 196, 8, 172, 122, 247, 245, 241, 93, 86, 43, 82, 230, 79, 2, 17, 0, 0, 0, 1, 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: