Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b880d048c5f0f33236cb3307527afebf7be09a4bdfa71b51f76413e15aef67b8

Tx prefix hash: 6c74054c574bc411b89be72e0d14a3bc008e6073f74e29298c3fe45d299b32a3
Tx public key: bf4a5f38e9b5ce9c718219f738ac4a7bbd3801d79e1b4f862687da1c463b14d1
Timestamp: 1704612032 Timestamp [UCT]: 2024-01-07 07:20:32 Age [y:d:h:m:s]: 01:069:16:16:27
Block: 929959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310925 RingCT/type: yes/0
Extra: 01bf4a5f38e9b5ce9c718219f738ac4a7bbd3801d79e1b4f862687da1c463b14d102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81d8291c0c57cc78069638d109edf675312df96adf359940e5f9798830ed3657 0.600000000000 1387837 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": 929969, "vin": [ { "gen": { "height": 929959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d8291c0c57cc78069638d109edf675312df96adf359940e5f9798830ed3657" } } ], "extra": [ 1, 191, 74, 95, 56, 233, 181, 206, 156, 113, 130, 25, 247, 56, 172, 74, 123, 189, 56, 1, 215, 158, 27, 79, 134, 38, 135, 218, 28, 70, 59, 20, 209, 2, 17, 0, 0, 0, 2, 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