Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c488e211e4cbd460153ad5618ca376a85f40735ebe466d4c67bf6d667aa22c77

Tx prefix hash: 7f519c4ceb938f98a1e1f1b1e911d20943c6de5c1a614e16c946c239609c0271
Tx public key: 9504fd2fe7f24de3809ddd66b035ea37754cbb1ccfb7a84bdbc5943ea18f175c
Timestamp: 1781661450 Timestamp [UTC]: 2026-06-17 01:57:30 Age [y:d:h:m:s]: 00:158:18:08:04
Block: 1561171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 122979 RingCT/type: yes/0
Extra: 019504fd2fe7f24de3809ddd66b035ea37754cbb1ccfb7a84bdbc5943ea18f175c02084c1cbdb1dcb08566

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 620aa2577b16af036174bda444d053fb0b361fca7b9d27e0a372b5351276797f 0.000600000000 2051149 of 15 <3e>

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": 1561181, "vin": [ { "gen": { "height": 1561171 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "620aa2577b16af036174bda444d053fb0b361fca7b9d27e0a372b5351276797f", "view_tag": "3e" } } } ], "extra": [ 1, 149, 4, 253, 47, 231, 242, 77, 227, 128, 157, 221, 102, 176, 53, 234, 55, 117, 76, 187, 28, 207, 183, 168, 75, 219, 197, 148, 62, 161, 143, 23, 92, 2, 8, 76, 28, 189, 177, 220, 176, 133, 102 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: