Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a8172e230ead26d15723598013b97525f44330764dc55f9d34359cc56cfe4e

Tx prefix hash: 2cc324b0d72e720c4c50db93b87851597007c773e77057609f220936010d58b5
Tx public key: cb9cae40f25c1be0f9393d1978cfd198e251b5f875f0b038c8f280e4431ea7c1
Timestamp: 1745530802 Timestamp [UCT]: 2025-04-24 21:40:02 Age [y:d:h:m:s]: 00:209:08:58:31
Block: 1268704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147356 RingCT/type: yes/0
Extra: 01cb9cae40f25c1be0f9393d1978cfd198e251b5f875f0b038c8f280e4431ea7c10211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8e29c7ae64a26a053283b07a54071ec760452e60bec237f07f9ec74ede224f2 0.600000000000 1755935 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 dinasty-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": 1268714, "vin": [ { "gen": { "height": 1268704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8e29c7ae64a26a053283b07a54071ec760452e60bec237f07f9ec74ede224f2" } } ], "extra": [ 1, 203, 156, 174, 64, 242, 92, 27, 224, 249, 57, 61, 25, 120, 207, 209, 152, 226, 81, 181, 248, 117, 240, 176, 56, 200, 242, 128, 228, 67, 30, 167, 193, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8