Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fd3ce107394a6bcf4bc933c60ee3a779f04df4e714073e92260c6ec5554d9fe

Tx prefix hash: e6d91d35e0055eaad84b34584f4e7eab62df4a0062c9368b0c9ffb81b3c2a96d
Tx public key: 91a0240d6322c0972cff63ae87c55c0880bcb96421f6754e527cd1521c1d6f93
Timestamp: 1713293737 Timestamp [UCT]: 2024-04-16 18:55:37 Age [y:d:h:m:s]: 00:212:09:44:27
Block: 1001940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152065 RingCT/type: yes/0
Extra: 0191a0240d6322c0972cff63ae87c55c0880bcb96421f6754e527cd1521c1d6f9302110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08dc75cd08b05336780a04457c72eb4f1e0b88176278d40c620cd7464cf3f539 0.600000000000 1462454 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": 1001950, "vin": [ { "gen": { "height": 1001940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08dc75cd08b05336780a04457c72eb4f1e0b88176278d40c620cd7464cf3f539" } } ], "extra": [ 1, 145, 160, 36, 13, 99, 34, 192, 151, 44, 255, 99, 174, 135, 197, 92, 8, 128, 188, 185, 100, 33, 246, 117, 78, 82, 124, 209, 82, 28, 29, 111, 147, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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