Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8bef24c2a3d0d8ae252cc6d3066fc2faa97c8fe8916b01629854f38a033cfae

Tx prefix hash: db4fa0f06303663cb398d81175f239bbe07cf1019627929b1d4d6a66d9a1ca18
Tx public key: bf94dd4a4ddb6c5e4ee39b8007fbc305cc8c066b4f4c7efec44bda909932ef10
Timestamp: 1770885448 Timestamp [UTC]: 2026-02-12 08:37:28 Age [y:d:h:m:s]: 00:276:06:33:10
Block: 1476099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 202876 RingCT/type: yes/0
Extra: 01bf94dd4a4ddb6c5e4ee39b8007fbc305cc8c066b4f4c7efec44bda909932ef10020885ab12ad63c1f3ea

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c5f4e4a4e6b6264eee6f7fdd05fd72e77cf3dec9ecda6d00ea6e30152305ce0b 0.000600000000 1965403 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": 1476109, "vin": [ { "gen": { "height": 1476099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5f4e4a4e6b6264eee6f7fdd05fd72e77cf3dec9ecda6d00ea6e30152305ce0b" } } ], "extra": [ 1, 191, 148, 221, 74, 77, 219, 108, 94, 78, 227, 155, 128, 7, 251, 195, 5, 204, 140, 6, 107, 79, 76, 126, 254, 196, 75, 218, 144, 153, 50, 239, 16, 2, 8, 133, 171, 18, 173, 99, 193, 243, 234 ], "rct_signatures": { "type": 0 } }


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