Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c2a4a429eab2134d080b8968df30d69151a7d188ced2bd9c8f3643bd332e08

Tx prefix hash: da702389f6dc1083437823f029b2b03a576f427bfb7c8c41888e84f0694039db
Tx public key: ce75549d7e3840d4069d4300de750a15681968e161e2c4e440a059279e7e3a7b
Timestamp: 1733473388 Timestamp [UCT]: 2024-12-06 08:23:08 Age [y:d:h:m:s]: 00:157:22:19:03
Block: 1169151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112695 RingCT/type: yes/0
Extra: 01ce75549d7e3840d4069d4300de750a15681968e161e2c4e440a059279e7e3a7b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0474eea04e7b929bc4e7a0e9df3fadc796a08f090bf1a1ac6303bfc0946e00 0.600000000000 1654864 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": 1169161, "vin": [ { "gen": { "height": 1169151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0474eea04e7b929bc4e7a0e9df3fadc796a08f090bf1a1ac6303bfc0946e00" } } ], "extra": [ 1, 206, 117, 84, 157, 126, 56, 64, 212, 6, 157, 67, 0, 222, 117, 10, 21, 104, 25, 104, 225, 97, 226, 196, 228, 64, 160, 89, 39, 158, 126, 58, 123, 2, 17, 0, 0, 0, 4, 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