Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb53d2aac810391656f867cc6f251ae6d7302e08e4614dae8eb12d99489f6d24

Tx prefix hash: d43a805cebd16b1f4befd52ca16679167c80059915d08e54654b5fe93fa6dacf
Tx public key: 96f44fddeb4c104f4af53bb86bbaf6075e79b6ee6e94d85c0309083c6ad02b85
Timestamp: 1697368151 Timestamp [UCT]: 2023-10-15 11:09:11 Age [y:d:h:m:s]: 01:174:19:48:53
Block: 870131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385970 RingCT/type: yes/0
Extra: 0196f44fddeb4c104f4af53bb86bbaf6075e79b6ee6e94d85c0309083c6ad02b85021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.803331535000 dcy

stealth address amount amount idx
00: 92813cca60c6f4b866056584d9d0fcfe0aaea4ee8235a65e8839c03bdae7b89e 0.803331535000 1325004 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": 870141, "vin": [ { "gen": { "height": 870131 } } ], "vout": [ { "amount": 803331535, "target": { "key": "92813cca60c6f4b866056584d9d0fcfe0aaea4ee8235a65e8839c03bdae7b89e" } } ], "extra": [ 1, 150, 244, 79, 221, 235, 76, 16, 79, 74, 245, 59, 184, 107, 186, 246, 7, 94, 121, 182, 238, 110, 148, 216, 92, 3, 9, 8, 60, 106, 208, 43, 133, 2, 17, 0, 0, 0, 9, 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