Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0f449cb10248119b3fa63eaa2a09c2ab8e4c91b64d2fc87466492102c252d4

Tx prefix hash: 0e2064ffb84f82db5ed23124d1b77796950bf14c107f7c79bc36f75b61ec5bf2
Tx public key: ed040ad808fdab13607fff41bdf2d4a4a07a6ac60579faed0b628b61f28579ad
Timestamp: 1769568704 Timestamp [UTC]: 2026-01-28 02:51:44 Age [y:d:h:m:s]: 00:289:04:30:07
Block: 1465170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212063 RingCT/type: yes/0
Extra: 01ed040ad808fdab13607fff41bdf2d4a4a07a6ac60579faed0b628b61f28579ad02110000000249d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba69710b2cc64b4be383db233211e369cb1814a2d6c865e9b47c87693cf0bff3 0.000600000000 1954396 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": 1465180, "vin": [ { "gen": { "height": 1465170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba69710b2cc64b4be383db233211e369cb1814a2d6c865e9b47c87693cf0bff3" } } ], "extra": [ 1, 237, 4, 10, 216, 8, 253, 171, 19, 96, 127, 255, 65, 189, 242, 212, 164, 160, 122, 106, 198, 5, 121, 250, 237, 11, 98, 139, 97, 242, 133, 121, 173, 2, 17, 0, 0, 0, 2, 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: