Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6de46c502dc9e1b28b16389e1a19692854290e31e5e96fee377a1f2366d456

Tx prefix hash: afe90fcccd0d092c7fa060f419561c29cc89ac9230f1f56ed62b7923d00d3780
Tx public key: d5fe5d5af1c183df4cfe2103330dd505aebd28c89f67b5dbf6d22248ad50cf05
Timestamp: 1702007159 Timestamp [UCT]: 2023-12-08 03:45:59 Age [y:d:h:m:s]: 01:039:20:16:30
Block: 908384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289845 RingCT/type: yes/0
Extra: 01d5fe5d5af1c183df4cfe2103330dd505aebd28c89f67b5dbf6d22248ad50cf05021100000010e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a889303bc9520ce7c68ab0aae25421997164ad24d473ed613aa11db413aa529 0.600000000000 1365415 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": 908394, "vin": [ { "gen": { "height": 908384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a889303bc9520ce7c68ab0aae25421997164ad24d473ed613aa11db413aa529" } } ], "extra": [ 1, 213, 254, 93, 90, 241, 193, 131, 223, 76, 254, 33, 3, 51, 13, 213, 5, 174, 189, 40, 200, 159, 103, 181, 219, 246, 210, 34, 72, 173, 80, 207, 5, 2, 17, 0, 0, 0, 16, 230, 210, 127, 156, 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