Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3eec07159877cf5eb8bde9a1b77b6593e489881a2ae76f44331570e1052a03

Tx prefix hash: 8c5e0ddbe0867ca610b23c7420042a0fa0c81ad021ec7de3a9d899f01a2f7e32
Tx public key: fb7e6ceb0a3927996d0cffa04d9d4972936e52337fae704d48b133508735df09
Timestamp: 1719450522 Timestamp [UCT]: 2024-06-27 01:08:42 Age [y:d:h:m:s]: 00:260:23:40:58
Block: 1052991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186500 RingCT/type: yes/0
Extra: 01fb7e6ceb0a3927996d0cffa04d9d4972936e52337fae704d48b133508735df090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dbe8628ceebcecff98e0d9b51549b92a3ed4db271a2fccd7b68f8cc5b9cacbd 0.600000000000 1523336 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": 1053001, "vin": [ { "gen": { "height": 1052991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dbe8628ceebcecff98e0d9b51549b92a3ed4db271a2fccd7b68f8cc5b9cacbd" } } ], "extra": [ 1, 251, 126, 108, 235, 10, 57, 39, 153, 109, 12, 255, 160, 77, 157, 73, 114, 147, 110, 82, 51, 127, 174, 112, 77, 72, 177, 51, 80, 135, 53, 223, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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