Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc611cf4a4ce82177a3f638fd09815c69d383e37f43ce69e4026caecc28ff51a

Tx prefix hash: c65693d6678df9cbdedf695e0807f6893d6712058661024e1e1199feb9cb7c5c
Tx public key: 0c0cdbde3a43858e241b6c1c6d380d912f98f30ccb9a108809f08d766e1cd7c8
Timestamp: 1665525477 Timestamp [UCT]: 2022-10-11 21:57:57 Age [y:d:h:m:s]: 02:137:04:24:10
Block: 607058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619561 RingCT/type: yes/0
Extra: 010c0cdbde3a43858e241b6c1c6d380d912f98f30ccb9a108809f08d766e1cd7c80211000000018b7b6602000000000000000000

1 output(s) for total of 5.978123651000 dcy

stealth address amount amount idx
00: e6953dc3a3628fffab4c118f74df3a6990c1811c27b4784dba9011d61f1ecd4a 5.978123651000 1043588 of 0

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": 607068, "vin": [ { "gen": { "height": 607058 } } ], "vout": [ { "amount": 5978123651, "target": { "key": "e6953dc3a3628fffab4c118f74df3a6990c1811c27b4784dba9011d61f1ecd4a" } } ], "extra": [ 1, 12, 12, 219, 222, 58, 67, 133, 142, 36, 27, 108, 28, 109, 56, 13, 145, 47, 152, 243, 12, 203, 154, 16, 136, 9, 240, 141, 118, 110, 28, 215, 200, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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