Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e9b54cb7ffaabf0ce86aa1f96c34e0cef4c9dda4c62e366f305531474aa042

Tx prefix hash: 8dc53551ec9a465b1e10430c9400a097d7c447ab058fb849b0a4f1e9eff6c964
Tx public key: d590201a4688eb4e975d2333c3a6ce66b5dfe1f4bd7a3ebd5f518b56ce88e514
Timestamp: 1728936683 Timestamp [UCT]: 2024-10-14 20:11:23 Age [y:d:h:m:s]: 00:186:11:17:40
Block: 1131639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133067 RingCT/type: yes/0
Extra: 01d590201a4688eb4e975d2333c3a6ce66b5dfe1f4bd7a3ebd5f518b56ce88e514021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26392c087272f574df241102b3d7a0f20ff5a07b82710090a371c69c14886e99 0.600000000000 1614542 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": 1131649, "vin": [ { "gen": { "height": 1131639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26392c087272f574df241102b3d7a0f20ff5a07b82710090a371c69c14886e99" } } ], "extra": [ 1, 213, 144, 32, 26, 70, 136, 235, 78, 151, 93, 35, 51, 195, 166, 206, 102, 181, 223, 225, 244, 189, 122, 62, 189, 95, 81, 139, 86, 206, 136, 229, 20, 2, 17, 0, 0, 0, 1, 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