Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b74bc993cc0af5daf89e183576758154da94205e9c4b0607a1d5f81f6359aa

Tx prefix hash: 0917b28b9d98ce4b1e1624004d09fe92a1b3b0b0713e8c7d0a6d30de6070701a
Tx public key: a0fc6e9215cfcc557d0548d82588c3f40767653dce9c290fb2a9c0d1068812e4
Timestamp: 1721030835 Timestamp [UCT]: 2024-07-15 08:07:15 Age [y:d:h:m:s]: 00:190:15:48:52
Block: 1066114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136364 RingCT/type: yes/0
Extra: 01a0fc6e9215cfcc557d0548d82588c3f40767653dce9c290fb2a9c0d1068812e4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c631f9749b674535746b3e539ad8a846fa0574fac796e10fb45b3a2c36ecd941 0.600000000000 1536687 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": 1066124, "vin": [ { "gen": { "height": 1066114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c631f9749b674535746b3e539ad8a846fa0574fac796e10fb45b3a2c36ecd941" } } ], "extra": [ 1, 160, 252, 110, 146, 21, 207, 204, 85, 125, 5, 72, 216, 37, 136, 195, 244, 7, 103, 101, 61, 206, 156, 41, 15, 178, 169, 192, 209, 6, 136, 18, 228, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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