Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0332c300e8c279d9931179e5927f699bcd71eca423e71024c01aa4da2a1b2a74

Tx prefix hash: bed5bb1f66956f8a3f4c290394a4cff7927bd31a4b451f251eeecedbea9453b8
Tx public key: 7499bfe117de3518e38a2b6f9ccc997aa44199e94b9036ece9596916c7b6c429
Timestamp: 1702010721 Timestamp [UCT]: 2023-12-08 04:45:21 Age [y:d:h:m:s]: 01:044:06:28:33
Block: 908408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292969 RingCT/type: yes/0
Extra: 017499bfe117de3518e38a2b6f9ccc997aa44199e94b9036ece9596916c7b6c429021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aca9df8d25d800621101eecb6df5bc4a32e94201db17554f3b67884e6db31517 0.600000000000 1365441 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": 908418, "vin": [ { "gen": { "height": 908408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aca9df8d25d800621101eecb6df5bc4a32e94201db17554f3b67884e6db31517" } } ], "extra": [ 1, 116, 153, 191, 225, 23, 222, 53, 24, 227, 138, 43, 111, 156, 204, 153, 122, 164, 65, 153, 233, 75, 144, 54, 236, 233, 89, 105, 22, 199, 182, 196, 41, 2, 17, 0, 0, 0, 4, 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