Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c4668fd1736255237c5989fee59576e9e7a5dbe0fd113774e41afa1ca7d0d8

Tx prefix hash: bfdb42975b4efbf6f57018f1915c944160c8b2e41b3e9cc608a63b266666f010
Tx public key: ebc8b6c7cb58fe271e892786820b72396e40b7d5649250c1d2c8b59e41a82700
Timestamp: 1739844537 Timestamp [UCT]: 2025-02-18 02:08:57 Age [y:d:h:m:s]: 00:233:01:28:19
Block: 1221602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164302 RingCT/type: yes/0
Extra: 01ebc8b6c7cb58fe271e892786820b72396e40b7d5649250c1d2c8b59e41a82700021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf0d5eccdbebb074c61ea2ffaf7308697ef02f2ef2fb0027da99ff043349667 0.600000000000 1708447 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": 1221612, "vin": [ { "gen": { "height": 1221602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf0d5eccdbebb074c61ea2ffaf7308697ef02f2ef2fb0027da99ff043349667" } } ], "extra": [ 1, 235, 200, 182, 199, 203, 88, 254, 39, 30, 137, 39, 134, 130, 11, 114, 57, 110, 64, 183, 213, 100, 146, 80, 193, 210, 200, 181, 158, 65, 168, 39, 0, 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