Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf50fd17557d6b551b5cea45d14dccc8da4b5712762af7afdf4626b3771c26dc

Tx prefix hash: 05f2f274c07d30f8cfbe6bb6c1ac0a81abe0c0c34e2b330d5f80d9ef858a7365
Tx public key: f9e9be970243fe5541516424ddb9547014be1b99ca094da10b31e81ba8548380
Timestamp: 1733807397 Timestamp [UCT]: 2024-12-10 05:09:57 Age [y:d:h:m:s]: 00:191:07:00:02
Block: 1171928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136404 RingCT/type: yes/0
Extra: 01f9e9be970243fe5541516424ddb9547014be1b99ca094da10b31e81ba8548380021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2ef1cdb9fb4d01a19c8fdbe5b22c893459c3913c3b184f8392ea73b824139f3 0.600000000000 1657753 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": 1171938, "vin": [ { "gen": { "height": 1171928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2ef1cdb9fb4d01a19c8fdbe5b22c893459c3913c3b184f8392ea73b824139f3" } } ], "extra": [ 1, 249, 233, 190, 151, 2, 67, 254, 85, 65, 81, 100, 36, 221, 185, 84, 112, 20, 190, 27, 153, 202, 9, 77, 161, 11, 49, 232, 27, 168, 84, 131, 128, 2, 17, 0, 0, 0, 4, 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