Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002ccc54232d7ef0e1c9b25aa688e321f0fd0489b25d84dab10835dcc593fe27

Tx prefix hash: 2f3701f1167d823f96563a6bf465e3d23e77315443afba0a0090659517823915
Tx public key: b0419f3599efea937d581fc81b91cde27334d8fb032d31e5737462cb3e499df6
Timestamp: 1747071446 Timestamp [UTC]: 2025-05-12 17:37:26 Age [y:d:h:m:s]: 01:192:12:11:52
Block: 1281454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401751 RingCT/type: yes/0
Extra: 01b0419f3599efea937d581fc81b91cde27334d8fb032d31e5737462cb3e499df60211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1e053b69ec2ee71cfb12db30c8a33013b7123bdc479a209a73ab3d0d75a4d4b3 0.000600000000 1768853 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": 1281464, "vin": [ { "gen": { "height": 1281454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e053b69ec2ee71cfb12db30c8a33013b7123bdc479a209a73ab3d0d75a4d4b3" } } ], "extra": [ 1, 176, 65, 159, 53, 153, 239, 234, 147, 125, 88, 31, 200, 27, 145, 205, 226, 115, 52, 216, 251, 3, 45, 49, 229, 115, 116, 98, 203, 62, 73, 157, 246, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: