Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d022ac13f8e7448e0f7f10f0cd93169a8a664a44e1ffcaab1772fb6b6be18761

Tx prefix hash: 147965e9e1a026d5470476c9b85394f75280ca1cffd6f20e26cd14291ff549ac
Tx public key: 208a75628a87f250e6e82860c0ea38c83f7ddbb207e8b8ce7d659f33a232ab3f
Timestamp: 1707874438 Timestamp [UCT]: 2024-02-14 01:33:58 Age [y:d:h:m:s]: 01:059:22:32:02
Block: 957026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303895 RingCT/type: yes/0
Extra: 01208a75628a87f250e6e82860c0ea38c83f7ddbb207e8b8ce7d659f33a232ab3f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4190e94eb5c1b75234297d16c802277f611dbdcab4b6f8b8e0fbb4bf77752936 0.600000000000 1416340 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": 957036, "vin": [ { "gen": { "height": 957026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4190e94eb5c1b75234297d16c802277f611dbdcab4b6f8b8e0fbb4bf77752936" } } ], "extra": [ 1, 32, 138, 117, 98, 138, 135, 242, 80, 230, 232, 40, 96, 192, 234, 56, 200, 63, 125, 219, 178, 7, 232, 184, 206, 125, 101, 159, 51, 162, 50, 171, 63, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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