Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37babc48d817b5095fff1be6522cabadd59bbbaa7eca21465a3ce14950080cbc

Tx prefix hash: 8f481632e3edbd181fae976d2734a37ce86a73a0f5e68411cf2f6b82228211cc
Tx public key: fbcb3c74f8ccdeb7f8efea6a2623245cc551b7ed57d5b8fd2956309a4e0df25d
Timestamp: 1645731475 Timestamp [UCT]: 2022-02-24 19:37:55 Age [y:d:h:m:s]: 02:320:03:10:07
Block: 445699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 748210 RingCT/type: yes/0
Extra: 01fbcb3c74f8ccdeb7f8efea6a2623245cc551b7ed57d5b8fd2956309a4e0df25d021100000004a272b9cb000000000000000000

1 output(s) for total of 20.474555385000 dcy

stealth address amount amount idx
00: 1ae155b7105d3c628d0370ea3c77e4e6ae2b8f5355c1b084e1378dba12bdd6b2 20.474555385000 859386 of 0

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": 445709, "vin": [ { "gen": { "height": 445699 } } ], "vout": [ { "amount": 20474555385, "target": { "key": "1ae155b7105d3c628d0370ea3c77e4e6ae2b8f5355c1b084e1378dba12bdd6b2" } } ], "extra": [ 1, 251, 203, 60, 116, 248, 204, 222, 183, 248, 239, 234, 106, 38, 35, 36, 92, 197, 81, 183, 237, 87, 213, 184, 253, 41, 86, 48, 154, 78, 13, 242, 93, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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