Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6903c187047ccc93cbbf35af91719490e03a50bde6b26b105d43290ea798f0a

Tx prefix hash: ce71229e6399e6b0cbc4fe27359fe9a5f712d4e20a2c4704f9b8ceb33488f071
Tx public key: 4cea35a3b906f1db0bff7acc548aa199614da4bba8723ea759e590e92ae4cdb5
Timestamp: 1703134478 Timestamp [UCT]: 2023-12-21 04:54:38 Age [y:d:h:m:s]: 01:143:20:36:54
Block: 917749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363945 RingCT/type: yes/0
Extra: 014cea35a3b906f1db0bff7acc548aa199614da4bba8723ea759e590e92ae4cdb5021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5fe5198ac376a592f6c4361db8c2f0740190c3fa28ee658c6db8f2d6e014fff 0.600000000000 1375331 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": 917759, "vin": [ { "gen": { "height": 917749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5fe5198ac376a592f6c4361db8c2f0740190c3fa28ee658c6db8f2d6e014fff" } } ], "extra": [ 1, 76, 234, 53, 163, 185, 6, 241, 219, 11, 255, 122, 204, 84, 138, 161, 153, 97, 77, 164, 187, 168, 114, 62, 167, 89, 229, 144, 233, 42, 228, 205, 181, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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