Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e45db368b2fa7e15a752dcdca275369ffd502bf571926041108c4af50fa6d599

Tx prefix hash: e5d139debcdf5cb4565c077535ba173e7b90318a271b3d019a7b8e2c78aae3e7
Tx public key: 2e6e927b4602c37820b5e17d2ebba299263f02656431a873c530b4e82b4b8ba6
Timestamp: 1734237927 Timestamp [UCT]: 2024-12-15 04:45:27 Age [y:d:h:m:s]: 00:109:22:05:25
Block: 1175503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78320 RingCT/type: yes/0
Extra: 012e6e927b4602c37820b5e17d2ebba299263f02656431a873c530b4e82b4b8ba60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a9ff9f9d12e5e28fdac1f3c2e53f0fde5f1730d2b546fe4c53c45aba9e13bf 0.600000000000 1661792 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": 1175513, "vin": [ { "gen": { "height": 1175503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a9ff9f9d12e5e28fdac1f3c2e53f0fde5f1730d2b546fe4c53c45aba9e13bf" } } ], "extra": [ 1, 46, 110, 146, 123, 70, 2, 195, 120, 32, 181, 225, 125, 46, 187, 162, 153, 38, 63, 2, 101, 100, 49, 168, 115, 197, 48, 180, 232, 43, 75, 139, 166, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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