Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f746a3531e231f466d965045128331eb327d743922cabb74e7bd67acd9b20917

Tx prefix hash: d140f331d9271fc73a9b56459f40fdb1d9bc8311a1c42c62c7e07ad3d4066286
Tx public key: 725ad374e62bef4bf73dbf09207f7b7811c3dfabfe7062ca8173f0be56b99ec7
Timestamp: 1732433647 Timestamp [UCT]: 2024-11-24 07:34:07 Age [y:d:h:m:s]: 00:145:01:51:51
Block: 1160540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103511 RingCT/type: yes/0
Extra: 01725ad374e62bef4bf73dbf09207f7b7811c3dfabfe7062ca8173f0be56b99ec7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5caeb9b7fd42cdcb19ddebb024e8d8eb4bf76c120a254fb07f2cdb6ed2f6b41 0.600000000000 1646187 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": 1160550, "vin": [ { "gen": { "height": 1160540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5caeb9b7fd42cdcb19ddebb024e8d8eb4bf76c120a254fb07f2cdb6ed2f6b41" } } ], "extra": [ 1, 114, 90, 211, 116, 230, 43, 239, 75, 247, 61, 191, 9, 32, 127, 123, 120, 17, 195, 223, 171, 254, 112, 98, 202, 129, 115, 240, 190, 86, 185, 158, 199, 2, 17, 0, 0, 0, 2, 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