Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea8c3b09f6ecebc5d74f6b95047f11f9dd999eb69a3c88621cb1338b2b80fa66

Tx prefix hash: 17e87fe4c06e91a77226c8fa3871bd816b96aaac24c9980c16213b471601e093
Tx public key: 9afe6110e909274a3af3542b0f449d7c21e4527ec971a75ffd4a216631f196e1
Timestamp: 1710463305 Timestamp [UCT]: 2024-03-15 00:41:45 Age [y:d:h:m:s]: 01:236:10:19:06
Block: 978516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427640 RingCT/type: yes/0
Extra: 019afe6110e909274a3af3542b0f449d7c21e4527ec971a75ffd4a216631f196e10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdf7ba328d07420b3a2c47090567e2955a1a66cfefc8d4511b343004418417b7 0.600000000000 1438543 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": 978526, "vin": [ { "gen": { "height": 978516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf7ba328d07420b3a2c47090567e2955a1a66cfefc8d4511b343004418417b7" } } ], "extra": [ 1, 154, 254, 97, 16, 233, 9, 39, 74, 58, 243, 84, 43, 15, 68, 157, 124, 33, 228, 82, 126, 201, 113, 167, 95, 253, 74, 33, 102, 49, 241, 150, 225, 2, 17, 0, 0, 0, 3, 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