Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda01de3976bf007214c2070e9faf4af794937c887c35cf0845b6454df0fbc90

Tx prefix hash: e71777832b4e8db040f8deced8cff4800289699fc194b60e4a76b86f584d52f4
Tx public key: 63aaf4475f6af13dfe211dc6a0a8d6168599798158e8e836fb1a71ebae337184
Timestamp: 1675494226 Timestamp [UCT]: 2023-02-04 07:03:46 Age [y:d:h:m:s]: 01:302:05:21:38
Block: 689461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476948 RingCT/type: yes/0
Extra: 0163aaf4475f6af13dfe211dc6a0a8d6168599798158e8e836fb1a71ebae3371840211000000015029cbac000000000000000000

1 output(s) for total of 3.188081586000 dcy

stealth address amount amount idx
00: b3b7c7224ad3c84d4aebdd5378d13e0d950d4b18ba588f82e075329f07f41c84 3.188081586000 1132137 of 0

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": 689471, "vin": [ { "gen": { "height": 689461 } } ], "vout": [ { "amount": 3188081586, "target": { "key": "b3b7c7224ad3c84d4aebdd5378d13e0d950d4b18ba588f82e075329f07f41c84" } } ], "extra": [ 1, 99, 170, 244, 71, 95, 106, 241, 61, 254, 33, 29, 198, 160, 168, 214, 22, 133, 153, 121, 129, 88, 232, 232, 54, 251, 26, 113, 235, 174, 51, 113, 132, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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