Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd497a9cb63b44759ae86fb6cfde153b19eb917feb7ea5b18639dbc973d994b9

Tx prefix hash: 6a2dc2d632e46f5a2f2dce2c05d4a86e79a3b02d3f523a084f8e751e91ecd8c3
Tx public key: 8c047dfe50af1832c9d8232beaa3ae074808046cb047340ec23e2ae1882e96e5
Timestamp: 1718708988 Timestamp [UCT]: 2024-06-18 11:09:48 Age [y:d:h:m:s]: 00:295:03:44:27
Block: 1046853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210918 RingCT/type: yes/0
Extra: 018c047dfe50af1832c9d8232beaa3ae074808046cb047340ec23e2ae1882e96e50211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f69f282f8a3ea7b183ec62544bffa51e728149da406c2f9c2ccaee884965a214 0.600000000000 1516672 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": 1046863, "vin": [ { "gen": { "height": 1046853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f69f282f8a3ea7b183ec62544bffa51e728149da406c2f9c2ccaee884965a214" } } ], "extra": [ 1, 140, 4, 125, 254, 80, 175, 24, 50, 201, 216, 35, 43, 234, 163, 174, 7, 72, 8, 4, 108, 176, 71, 52, 14, 194, 62, 42, 225, 136, 46, 150, 229, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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