Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d895ee6ea2efe70acb8f04fbecab9564bf405839f13cb192e9ab7c2942baf149

Tx prefix hash: c48cad1a22bffa5a786cbe7aec875be52de9976a347ce85ac4be086f71ce35ae
Tx public key: 6420c092e0a3980db3b3224e23f6e5bb5e48048a4c500b4ccf1da9261a1ca223
Timestamp: 1721496583 Timestamp [UCT]: 2024-07-20 17:29:43 Age [y:d:h:m:s]: 00:298:07:23:12
Block: 1069957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213154 RingCT/type: yes/0
Extra: 016420c092e0a3980db3b3224e23f6e5bb5e48048a4c500b4ccf1da9261a1ca2230211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bebf26039f05d89aae277dad9740f4b9dfe5b09b8fe0a1247b0e86b94a538136 0.600000000000 1541594 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": 1069967, "vin": [ { "gen": { "height": 1069957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bebf26039f05d89aae277dad9740f4b9dfe5b09b8fe0a1247b0e86b94a538136" } } ], "extra": [ 1, 100, 32, 192, 146, 224, 163, 152, 13, 179, 179, 34, 78, 35, 246, 229, 187, 94, 72, 4, 138, 76, 80, 11, 76, 207, 29, 169, 38, 26, 28, 162, 35, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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