Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48faca0f27c2d47482a82341239c47da486e56004429a2c899ceee2f5bd597ca

Tx prefix hash: 59f9f9b712ccab21a6934f94010f4a3bfa5f3313a270a457f7d4f4e3ddd1f19e
Tx public key: 1cba0818f7bf674c07d74c0f09e1c1cbbb678dc3dde9038337baaef1fe154dc7
Timestamp: 1702884100 Timestamp [UCT]: 2023-12-18 07:21:40 Age [y:d:h:m:s]: 01:143:02:23:36
Block: 915655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363425 RingCT/type: yes/0
Extra: 011cba0818f7bf674c07d74c0f09e1c1cbbb678dc3dde9038337baaef1fe154dc702110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a159d43dcc04e025a24d3c0d54608cae06a08130bae4e7426e6551cfead8bfd3 0.600000000000 1373051 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": 915665, "vin": [ { "gen": { "height": 915655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a159d43dcc04e025a24d3c0d54608cae06a08130bae4e7426e6551cfead8bfd3" } } ], "extra": [ 1, 28, 186, 8, 24, 247, 191, 103, 76, 7, 215, 76, 15, 9, 225, 193, 203, 187, 103, 141, 195, 221, 233, 3, 131, 55, 186, 174, 241, 254, 21, 77, 199, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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