Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab4070b6cecba501c2ef39e53e971155d1f194459c4a8bb7f5fd8580585869a

Tx prefix hash: 1498984c727e059cbdf9e2c81e7d167d88844c5465692377a6c21696b650f794
Tx public key: 60d73633e05cfd70a1edce9db9e8de19437a12cbbf5ebd3ff905688b814d9b1e
Timestamp: 1725994021 Timestamp [UCT]: 2024-09-10 18:47:01 Age [y:d:h:m:s]: 01:061:05:56:49
Block: 1107251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302195 RingCT/type: yes/0
Extra: 0160d73633e05cfd70a1edce9db9e8de19437a12cbbf5ebd3ff905688b814d9b1e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a88935168098d07c8d9a2b0b98ef1ebbd17aa3dd6d269b622efc2bfde113116 0.600000000000 1584862 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": 1107261, "vin": [ { "gen": { "height": 1107251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a88935168098d07c8d9a2b0b98ef1ebbd17aa3dd6d269b622efc2bfde113116" } } ], "extra": [ 1, 96, 215, 54, 51, 224, 92, 253, 112, 161, 237, 206, 157, 185, 232, 222, 25, 67, 122, 18, 203, 191, 94, 189, 63, 249, 5, 104, 139, 129, 77, 155, 30, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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