Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcd766c61533f940fba097078f9642a134ee5e8fb326c11e3aa8ae5f115493af

Tx prefix hash: b6c6c6b9ae82ef87a7ab4592b07ca377ab4a345612f38cac18ec6cad39369377
Tx public key: a2aa4124415ec341bc73e33c0341d373289cd0f8fad659f3ba8bacbd2b28ff49
Timestamp: 1746109165 Timestamp [UCT]: 2025-05-01 14:19:25 Age [y:d:h:m:s]: 00:204:06:57:49
Block: 1273489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143725 RingCT/type: yes/0
Extra: 01a2aa4124415ec341bc73e33c0341d373289cd0f8fad659f3ba8bacbd2b28ff4902110000000c9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 833138ccdb3c9d3ecc792d3a0aae9a2e9c5da794f4869ff1d34fe680b6462523 0.600000000000 1760772 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": 1273499, "vin": [ { "gen": { "height": 1273489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "833138ccdb3c9d3ecc792d3a0aae9a2e9c5da794f4869ff1d34fe680b6462523" } } ], "extra": [ 1, 162, 170, 65, 36, 65, 94, 195, 65, 188, 115, 227, 60, 3, 65, 211, 115, 40, 156, 208, 248, 250, 214, 89, 243, 186, 139, 172, 189, 43, 40, 255, 73, 2, 17, 0, 0, 0, 12, 159, 159, 230, 140, 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