Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cee1dface7ebc43c207734a5a9ffea9ac3052f3c5f396a1fa3ae4a9873c69c0

Tx prefix hash: 1c825677bd81b58e9e27e44524080d0a5514996657d76364633199db23c0a1a4
Tx public key: 1018a730740fe2e8b5b9c7d10984a6dfeb0cce8bcdc7df4dea25757197aa8e07
Timestamp: 1720911948 Timestamp [UCT]: 2024-07-13 23:05:48 Age [y:d:h:m:s]: 00:261:06:59:47
Block: 1065129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186655 RingCT/type: yes/0
Extra: 011018a730740fe2e8b5b9c7d10984a6dfeb0cce8bcdc7df4dea25757197aa8e0702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 489c0f197e6a2830650135c5b8d87706734de5d91b578d8c7e877d2a73c62be0 0.600000000000 1535672 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": 1065139, "vin": [ { "gen": { "height": 1065129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "489c0f197e6a2830650135c5b8d87706734de5d91b578d8c7e877d2a73c62be0" } } ], "extra": [ 1, 16, 24, 167, 48, 116, 15, 226, 232, 181, 185, 199, 209, 9, 132, 166, 223, 235, 12, 206, 139, 205, 199, 223, 77, 234, 37, 117, 113, 151, 170, 142, 7, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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