Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c8fc570f36521620942af1fefa5370064de19c8009d9df50590e835e0368c57

Tx prefix hash: 834414f246ce94b5e3b1d75b499806c5b91373a2cf082d5ac3e24474695b0663
Tx public key: 96aeab4f86212ef4c88d9b334be95edaa5fce40758e9f64b1ccb6efe5bc85f87
Timestamp: 1731302657 Timestamp [UCT]: 2024-11-11 05:24:17 Age [y:d:h:m:s]: 00:013:23:53:19
Block: 1151164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10015 RingCT/type: yes/0
Extra: 0196aeab4f86212ef4c88d9b334be95edaa5fce40758e9f64b1ccb6efe5bc85f87021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b679dc5678717bf5b58c14c75c8f5bde434a1374cabc68699cba943513c20e92 0.600000000000 1636641 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": 1151174, "vin": [ { "gen": { "height": 1151164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b679dc5678717bf5b58c14c75c8f5bde434a1374cabc68699cba943513c20e92" } } ], "extra": [ 1, 150, 174, 171, 79, 134, 33, 46, 244, 200, 141, 155, 51, 75, 233, 94, 218, 165, 252, 228, 7, 88, 233, 246, 75, 28, 203, 110, 254, 91, 200, 95, 135, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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