Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0841f6681351cbc2c4ac39360e714556a2dc5fb3723051c5eed35f571069cd

Tx prefix hash: 9bbaeebd66175e408d63f8b8d9f18fcb1a76064d390a3d43110649331738166b
Tx public key: 3414534cd8493d2eea6a8c01d342f5eabf9581a3d8e2ebe8a79341c2983b0a67
Timestamp: 1705857131 Timestamp [UCT]: 2024-01-21 17:12:11 Age [y:d:h:m:s]: 01:071:05:25:33
Block: 940275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311989 RingCT/type: yes/0
Extra: 013414534cd8493d2eea6a8c01d342f5eabf9581a3d8e2ebe8a79341c2983b0a670211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02c940eda0d4409dc304e882a86a4decaa1ee9d48564b5f4015d12a6373726c8 0.600000000000 1398411 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": 940285, "vin": [ { "gen": { "height": 940275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02c940eda0d4409dc304e882a86a4decaa1ee9d48564b5f4015d12a6373726c8" } } ], "extra": [ 1, 52, 20, 83, 76, 216, 73, 61, 46, 234, 106, 140, 1, 211, 66, 245, 234, 191, 149, 129, 163, 216, 226, 235, 232, 167, 147, 65, 194, 152, 59, 10, 103, 2, 17, 0, 0, 0, 5, 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