Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7947c452e0f55a210b472efadf87447d8b4d9aa718e8aa7bf5491c7b814774a8

Tx prefix hash: cee3ea2418e8b46ab21841caad6570520820166a37482a5ee82e9bae281d8c90
Tx public key: 6c2c4f45730b3a629f13a4042ba068d2909299752e862874d37970cc0d5d450b
Timestamp: 1716511712 Timestamp [UCT]: 2024-05-24 00:48:32 Age [y:d:h:m:s]: 00:297:11:44:10
Block: 1028644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212626 RingCT/type: yes/0
Extra: 016c2c4f45730b3a629f13a4042ba068d2909299752e862874d37970cc0d5d450b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d18023bd120a1d45c9eeca3a3d8b582f3cce9123fc56024273c7604a1c07d030 0.600000000000 1496639 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": 1028654, "vin": [ { "gen": { "height": 1028644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d18023bd120a1d45c9eeca3a3d8b582f3cce9123fc56024273c7604a1c07d030" } } ], "extra": [ 1, 108, 44, 79, 69, 115, 11, 58, 98, 159, 19, 164, 4, 43, 160, 104, 210, 144, 146, 153, 117, 46, 134, 40, 116, 211, 121, 112, 204, 13, 93, 69, 11, 2, 17, 0, 0, 0, 1, 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