Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fb241e783985c5153ac24d85e858c4c6cc6e31e11f52aa5f7005af3046535ed

Tx prefix hash: 1658a69e44f7c628762d1c042378e06699c9f57ecc19f39a6411e88bafda29c4
Tx public key: 1101b670c815da814e4638fb8a53635f48d9abf5669adc53b8e721211d26e031
Timestamp: 1711858323 Timestamp [UCT]: 2024-03-31 04:12:03 Age [y:d:h:m:s]: 00:242:15:14:19
Block: 990081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173677 RingCT/type: yes/0
Extra: 011101b670c815da814e4638fb8a53635f48d9abf5669adc53b8e721211d26e03102110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c021c88f4e1fedb432a9ee39bd48bf1a937df751310f44f0edd373b92ada9175 0.600000000000 1450403 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": 990091, "vin": [ { "gen": { "height": 990081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c021c88f4e1fedb432a9ee39bd48bf1a937df751310f44f0edd373b92ada9175" } } ], "extra": [ 1, 17, 1, 182, 112, 200, 21, 218, 129, 78, 70, 56, 251, 138, 83, 99, 95, 72, 217, 171, 245, 102, 154, 220, 83, 184, 231, 33, 33, 29, 38, 224, 49, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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