Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6631e355862ace404df4a5076321e24f458e5c121d17788d2d9cdfa7ab3de44f

Tx prefix hash: 2db7a63108b539aebf21243830d9cd170694979b4dc5935a2f250ad702ccf2d6
Tx public key: c21d58ec1024896df4e304e3aa6ef879ecf2220dbdf60de8d436507415acb2b0
Timestamp: 1713134197 Timestamp [UCT]: 2024-04-14 22:36:37 Age [y:d:h:m:s]: 01:206:23:42:01
Block: 1000616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406614 RingCT/type: yes/0
Extra: 01c21d58ec1024896df4e304e3aa6ef879ecf2220dbdf60de8d436507415acb2b0021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8c0ea5b0a6690ce359596b6953b85c4e8943ed7344ce40fe1e24743457c9f1e 0.600000000000 1461114 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": 1000626, "vin": [ { "gen": { "height": 1000616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c0ea5b0a6690ce359596b6953b85c4e8943ed7344ce40fe1e24743457c9f1e" } } ], "extra": [ 1, 194, 29, 88, 236, 16, 36, 137, 109, 244, 227, 4, 227, 170, 110, 248, 121, 236, 242, 34, 13, 189, 246, 13, 232, 212, 54, 80, 116, 21, 172, 178, 176, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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