Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ca32e68f168a71d69584a3d3301253f014e86fbeb948034bd94ec361463f82

Tx prefix hash: 7a47f6f53895ce7189343f8dba91d4cac4b7e6234703ac5f75f016c06241a694
Tx public key: 61f7d0f271ebaede705dddb232f27bae360cc8b54f6893b9d5b7ebb6f11a2b07
Timestamp: 1734868411 Timestamp [UCT]: 2024-12-22 11:53:31 Age [y:d:h:m:s]: 00:093:17:30:45
Block: 1180731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66735 RingCT/type: yes/0
Extra: 0161f7d0f271ebaede705dddb232f27bae360cc8b54f6893b9d5b7ebb6f11a2b07021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9c2d29a2224cf8e0265b0e5dac053163ee8b8ee5c57a68b2c9650492e07c616 0.600000000000 1667144 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": 1180741, "vin": [ { "gen": { "height": 1180731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9c2d29a2224cf8e0265b0e5dac053163ee8b8ee5c57a68b2c9650492e07c616" } } ], "extra": [ 1, 97, 247, 208, 242, 113, 235, 174, 222, 112, 93, 221, 178, 50, 242, 123, 174, 54, 12, 200, 181, 79, 104, 147, 185, 213, 183, 235, 182, 241, 26, 43, 7, 2, 17, 0, 0, 0, 4, 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