Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c02193ebe477d38496210b5d731c5cf3a691562b89ffbb8166da6e418b9272f

Tx prefix hash: b86d19ff70d79bbc79b5d19342711d7e0b2abf234cee02f2c1ca820ce62ea48d
Tx public key: 93c455528abb0ba5fd870c153c0cd95bb38b46e51f95214ef68d3e9362864408
Timestamp: 1711056216 Timestamp [UCT]: 2024-03-21 21:23:36 Age [y:d:h:m:s]: 00:340:14:54:21
Block: 983432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243491 RingCT/type: yes/0
Extra: 0193c455528abb0ba5fd870c153c0cd95bb38b46e51f95214ef68d3e936286440802110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7e3f9d4b19290b6c1c5ae40487fc4fb777d11a5b44f7d24e22b4bce82a119e6 0.600000000000 1443563 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": 983442, "vin": [ { "gen": { "height": 983432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7e3f9d4b19290b6c1c5ae40487fc4fb777d11a5b44f7d24e22b4bce82a119e6" } } ], "extra": [ 1, 147, 196, 85, 82, 138, 187, 11, 165, 253, 135, 12, 21, 60, 12, 217, 91, 179, 139, 70, 229, 31, 149, 33, 78, 246, 141, 62, 147, 98, 134, 68, 8, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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