Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84bcbd7a7b73e87ce80e51e193307ecabb74876a3f0e461bde6e4504e2101a79

Tx prefix hash: 00b0638ea6c4280439af7f907b4687060bbfc3fa58632ca30fbc9c5a61227bbe
Tx public key: a2fdd6f8b496beb94531ba7cb3c8886c03a6fdec501875e99ba4e03fe6ca9b19
Timestamp: 1734555107 Timestamp [UCT]: 2024-12-18 20:51:47 Age [y:d:h:m:s]: 00:096:14:29:37
Block: 1178142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68794 RingCT/type: yes/0
Extra: 01a2fdd6f8b496beb94531ba7cb3c8886c03a6fdec501875e99ba4e03fe6ca9b19021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a149a8c0d5ac78a316e8624093ab418e34a17395a397e5ebfe9c917f733dd2da 0.600000000000 1664527 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": 1178152, "vin": [ { "gen": { "height": 1178142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a149a8c0d5ac78a316e8624093ab418e34a17395a397e5ebfe9c917f733dd2da" } } ], "extra": [ 1, 162, 253, 214, 248, 180, 150, 190, 185, 69, 49, 186, 124, 179, 200, 136, 108, 3, 166, 253, 236, 80, 24, 117, 233, 155, 164, 224, 63, 230, 202, 155, 25, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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