Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f72af6f0e776613734c5fe5d65f4a56d409c80c5ace00b04dcf5d7051be9394

Tx prefix hash: 93a8e9b8c4ff3dd9a9995ed1fa73711c952811c377e9b434c311d2a9f1ceee39
Tx public key: 428297a12f08822a7d8ae50e17773c7398be2c5b9034429e003e0fbc3a31ec1e
Timestamp: 1734599719 Timestamp [UCT]: 2024-12-19 09:15:19 Age [y:d:h:m:s]: 00:131:22:11:47
Block: 1178504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94076 RingCT/type: yes/0
Extra: 01428297a12f08822a7d8ae50e17773c7398be2c5b9034429e003e0fbc3a31ec1e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be2825c262048f9150d77690e9160347cfcda83fd7808723422f7ee84ef463a1 0.600000000000 1664891 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": 1178514, "vin": [ { "gen": { "height": 1178504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be2825c262048f9150d77690e9160347cfcda83fd7808723422f7ee84ef463a1" } } ], "extra": [ 1, 66, 130, 151, 161, 47, 8, 130, 42, 125, 138, 229, 14, 23, 119, 60, 115, 152, 190, 44, 91, 144, 52, 66, 158, 0, 62, 15, 188, 58, 49, 236, 30, 2, 17, 0, 0, 0, 3, 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