Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c15cbe39fc81bb95a044b94d37ac1c039953d6ca4cd09e6b9ca0d515a0b9948

Tx prefix hash: 27945ae153908c9309b585a5bc69c3b9f1b0642a6952a6bb07cdc998d38fcec0
Tx public key: bd3337ca83a7263bbdd09a3a46a5556932b8ee514a9a5244d08aa7897cd44f03
Timestamp: 1710153609 Timestamp [UCT]: 2024-03-11 10:40:09 Age [y:d:h:m:s]: 01:098:20:26:04
Block: 975939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331556 RingCT/type: yes/0
Extra: 01bd3337ca83a7263bbdd09a3a46a5556932b8ee514a9a5244d08aa7897cd44f0302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d855dd2de649d778f4ff0a64f08c372fa5e714158592d40eb0c1dae1ec23e10d 0.600000000000 1435916 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": 975949, "vin": [ { "gen": { "height": 975939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d855dd2de649d778f4ff0a64f08c372fa5e714158592d40eb0c1dae1ec23e10d" } } ], "extra": [ 1, 189, 51, 55, 202, 131, 167, 38, 59, 189, 208, 154, 58, 70, 165, 85, 105, 50, 184, 238, 81, 74, 154, 82, 68, 208, 138, 167, 137, 124, 212, 79, 3, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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