Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b48e8398f0d0b1f3a52d3b91eaff615ea1b7a17673dc9cf6785d067335ce4b

Tx prefix hash: 97ee7d5589efe9af58d4fd0299a973eedf357a5af5b544b3fc06ce8c1aa635ab
Tx public key: 4adc7874f8a29c4f6c5a2607e6316c291f54711999c34d06ca5b7c75d6472fef
Timestamp: 1736242364 Timestamp [UTC]: 2025-01-07 09:32:44 Age [y:d:h:m:s]: 01:318:06:08:12
Block: 1192081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491413 RingCT/type: yes/0
Extra: 014adc7874f8a29c4f6c5a2607e6316c291f54711999c34d06ca5b7c75d6472fef02110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f339d94938dd0d6abc1bec2c275be051771ba6acf3b7cebfe2e2900e79f65bb3 0.000600000000 1678626 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": 1192091, "vin": [ { "gen": { "height": 1192081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f339d94938dd0d6abc1bec2c275be051771ba6acf3b7cebfe2e2900e79f65bb3" } } ], "extra": [ 1, 74, 220, 120, 116, 248, 162, 156, 79, 108, 90, 38, 7, 230, 49, 108, 41, 31, 84, 113, 25, 153, 195, 77, 6, 202, 91, 124, 117, 214, 71, 47, 239, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: