Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f99fbc5255301b9b4e3f8fb955b7e982befe6381a4fae70e42c80564c54f64

Tx prefix hash: 0653f82a00ca93785b2ad678a854eb78b104dc3a2ed7412dbe3c449056bc249c
Tx public key: 7c2bd8b3f34d11f7d802658d8ae0bbd19bca3a052b0ae643ae1559e5b12b1435
Timestamp: 1723913860 Timestamp [UCT]: 2024-08-17 16:57:40 Age [y:d:h:m:s]: 00:244:12:47:25
Block: 1090006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174636 RingCT/type: yes/0
Extra: 017c2bd8b3f34d11f7d802658d8ae0bbd19bca3a052b0ae643ae1559e5b12b143502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e41745ebf746f522b0f04b26493b6770e317e2e09b11baccac385ecd038a9be 0.600000000000 1564629 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": 1090016, "vin": [ { "gen": { "height": 1090006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e41745ebf746f522b0f04b26493b6770e317e2e09b11baccac385ecd038a9be" } } ], "extra": [ 1, 124, 43, 216, 179, 243, 77, 17, 247, 216, 2, 101, 141, 138, 224, 187, 209, 155, 202, 58, 5, 43, 10, 230, 67, 174, 21, 89, 229, 177, 43, 20, 53, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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