Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6218bc8bc35f8f13ac6ccd628cc555e213f6dbc40406a930938dccd92907b626

Tx prefix hash: 44c1224871765051df8313000f9e9f2b11f95e385f4b41614a87d7dd25c8e470
Tx public key: 2596b070175ff425f180c390a02d7b966e14b72b8c0df15bfb972b5c70c6c8bb
Timestamp: 1708216342 Timestamp [UCT]: 2024-02-18 00:32:22 Age [y:d:h:m:s]: 00:355:18:11:22
Block: 959856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254408 RingCT/type: yes/0
Extra: 012596b070175ff425f180c390a02d7b966e14b72b8c0df15bfb972b5c70c6c8bb02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dac5a32cf345ebb54ae472f8c55c20f32aa20317070579f13757480f616ee1d5 0.600000000000 1419415 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": 959866, "vin": [ { "gen": { "height": 959856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dac5a32cf345ebb54ae472f8c55c20f32aa20317070579f13757480f616ee1d5" } } ], "extra": [ 1, 37, 150, 176, 112, 23, 95, 244, 37, 241, 128, 195, 144, 160, 45, 123, 150, 110, 20, 183, 43, 140, 13, 241, 91, 251, 151, 43, 92, 112, 198, 200, 187, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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