Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec0a1bcf87b7aa06619f2d72dd5c53ad21b0fcaaa48ff5bec0304662c14d9c1

Tx prefix hash: 9aae4d28024ba0619b1eb7318cfef00c8000cb73d7a3621f5f8240cb9e3b2cc9
Tx public key: ac91d1caecbfa4420e395362162986d40df910b9fff4d66fb21f458f91970355
Timestamp: 1698517288 Timestamp [UTC]: 2023-10-28 18:21:28 Age [y:d:h:m:s]: 02:197:16:56:48
Block: 879668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653141 RingCT/type: yes/0
Extra: 01ac91d1caecbfa4420e395362162986d40df910b9fff4d66fb21f458f9197035502110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.000746955555 xmr

stealth address amount amount idx tag
00: 49f2d12ca7d2cfa689dc99d3c289b5901bce3b4750f8ae53c727cfd6d4ce3272 0.000746955555 1335202 of 0 -

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": 879678, "vin": [ { "gen": { "height": 879668 } } ], "vout": [ { "amount": 746955555, "target": { "key": "49f2d12ca7d2cfa689dc99d3c289b5901bce3b4750f8ae53c727cfd6d4ce3272" } } ], "extra": [ 1, 172, 145, 209, 202, 236, 191, 164, 66, 14, 57, 83, 98, 22, 41, 134, 212, 13, 249, 16, 185, 255, 244, 214, 111, 178, 31, 69, 143, 145, 151, 3, 85, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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: