Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 608745a648be396ed12334fa2e1b58cca60271ce1592506ba6058b1674090146

Tx prefix hash: 19116c4a73cdb7678da758a0ad24396c488d28f42b6ab3985a963860688868c2
Tx public key: 22f631542fcd9ff174d97449cd1efdfc253c427b73d0dfdfe7dcbfd3441f7b82
Timestamp: 1727618021 Timestamp [UCT]: 2024-09-29 13:53:41 Age [y:d:h:m:s]: 00:115:02:53:03
Block: 1120716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82259 RingCT/type: yes/0
Extra: 0122f631542fcd9ff174d97449cd1efdfc253c427b73d0dfdfe7dcbfd3441f7b8202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ba5ba5eae1617c668a2c9a6e2a8c8236a2ca95e048de72db0bce94d5b8d23db 0.600000000000 1602729 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": 1120726, "vin": [ { "gen": { "height": 1120716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ba5ba5eae1617c668a2c9a6e2a8c8236a2ca95e048de72db0bce94d5b8d23db" } } ], "extra": [ 1, 34, 246, 49, 84, 47, 205, 159, 241, 116, 217, 116, 73, 205, 30, 253, 252, 37, 60, 66, 123, 115, 208, 223, 223, 231, 220, 191, 211, 68, 31, 123, 130, 2, 17, 0, 0, 0, 10, 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