Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c55c396b8e24be968fbd991507c95dbe2c7ccd44831fbe970a7fefb4f79031

Tx prefix hash: d8147c19de73e8c5a6b9c902744c05793eabddd5a496219de29b676eeb16bf96
Tx public key: 778c684d9dbc09d63e1b9cc38d3e54a78f09157a447083aaa450fad1398dfdc8
Timestamp: 1718960549 Timestamp [UCT]: 2024-06-21 09:02:29 Age [y:d:h:m:s]: 01:138:16:46:27
Block: 1048923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357683 RingCT/type: yes/0
Extra: 01778c684d9dbc09d63e1b9cc38d3e54a78f09157a447083aaa450fad1398dfdc802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b821fe235f44aded39fffe714b1ec7b55687ed725edc6d8c04c90d48b68bf6 0.600000000000 1519014 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": 1048933, "vin": [ { "gen": { "height": 1048923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b821fe235f44aded39fffe714b1ec7b55687ed725edc6d8c04c90d48b68bf6" } } ], "extra": [ 1, 119, 140, 104, 77, 157, 188, 9, 214, 62, 27, 156, 195, 141, 62, 84, 167, 143, 9, 21, 122, 68, 112, 131, 170, 164, 80, 250, 209, 57, 141, 253, 200, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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