Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84a567bde5c3a4c5ec2b0a3122a22828b2427676decedc83bc2116f4c33f19e5

Tx prefix hash: 357acb42b5ec9dc1ce0aca26cd13c56ad8e97832096fbf10793f9f4ff9122c17
Tx public key: e79ba37f6e4526093a214a7c3fb0895ab816898f30732626288b943bc0519e1c
Timestamp: 1735244760 Timestamp [UCT]: 2024-12-26 20:26:00 Age [y:d:h:m:s]: 00:355:01:14:30
Block: 1183817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251311 RingCT/type: yes/0
Extra: 01e79ba37f6e4526093a214a7c3fb0895ab816898f30732626288b943bc0519e1c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f9e27eafe8ff1439e4d9822ef2be0398080fed679bad3c5a9c4f13be1d9198 0.600000000000 1670266 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": 1183827, "vin": [ { "gen": { "height": 1183817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f9e27eafe8ff1439e4d9822ef2be0398080fed679bad3c5a9c4f13be1d9198" } } ], "extra": [ 1, 231, 155, 163, 127, 110, 69, 38, 9, 58, 33, 74, 124, 63, 176, 137, 90, 184, 22, 137, 143, 48, 115, 38, 38, 40, 139, 148, 59, 192, 81, 158, 28, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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