Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19a117090ffc47312b6e8a509b902f73bf9bdfe84166044965e601e7ce5f4c21

Tx prefix hash: c7951449d01e6097eafd55c2216d93297f7171dce18b2f29ed1e647582e310c1
Tx public key: 34aadea0ce144a40d624175bdcec35170de1598a54d6f872e73bd21882c2d5b6
Timestamp: 1732010959 Timestamp [UCT]: 2024-11-19 10:09:19 Age [y:d:h:m:s]: 00:212:10:32:10
Block: 1157041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151551 RingCT/type: yes/0
Extra: 0134aadea0ce144a40d624175bdcec35170de1598a54d6f872e73bd21882c2d5b6021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2eaea2c2f8343db0d4b80c218074d250cf8c43e8bb2fafb64f9ceb83b929807 0.600000000000 1642664 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": 1157051, "vin": [ { "gen": { "height": 1157041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2eaea2c2f8343db0d4b80c218074d250cf8c43e8bb2fafb64f9ceb83b929807" } } ], "extra": [ 1, 52, 170, 222, 160, 206, 20, 74, 64, 214, 36, 23, 91, 220, 236, 53, 23, 13, 225, 89, 138, 84, 214, 248, 114, 231, 59, 210, 24, 130, 194, 213, 182, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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