Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735eddcfb75439e81c8797d0e4b7dd80f73e50104fcd869e563856ff90131db0

Tx prefix hash: bc1d2ccf5b2992c8302df5fcd2d5a74e01b5d4e4302ece1fadd08062a59ae5d6
Tx public key: 74a95555afc40386773787a33a10daf7719e8969952a147a24e555a9d582ff10
Timestamp: 1581946716 Timestamp [UCT]: 2020-02-17 13:38:36 Age [y:d:h:m:s]: 05:072:05:05:18
Block: 66675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204808 RingCT/type: yes/0
Extra: 0174a95555afc40386773787a33a10daf7719e8969952a147a24e555a9d582ff1002110000000112c4732d000000000000000000

1 output(s) for total of 369.044600419000 dcy

stealth address amount amount idx
00: 4ad03d90d2809f7ce7f9eee4024f9dcd3a7a4c213ceec6b2c0ae0671bca1d865 369.044600419000 122836 of 0

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": 66685, "vin": [ { "gen": { "height": 66675 } } ], "vout": [ { "amount": 369044600419, "target": { "key": "4ad03d90d2809f7ce7f9eee4024f9dcd3a7a4c213ceec6b2c0ae0671bca1d865" } } ], "extra": [ 1, 116, 169, 85, 85, 175, 196, 3, 134, 119, 55, 135, 163, 58, 16, 218, 247, 113, 158, 137, 105, 149, 42, 20, 122, 36, 229, 85, 169, 213, 130, 255, 16, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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