Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc054f21fc49a82201f7a4b26a50f55c47e71c5db8abb3af33f2c63aa1dd6832

Tx prefix hash: c7906a2e0f3714a0d40716dd5196b623fbfe32a031a6d8a7a5834327a5efa2a8
Tx public key: 0528405d18dc623086f06a7b52eb0ab3b4981cd5f487e77594871193d4b3fbd1
Timestamp: 1726887997 Timestamp [UCT]: 2024-09-21 03:06:37 Age [y:d:h:m:s]: 00:064:04:58:31
Block: 1114665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45890 RingCT/type: yes/0
Extra: 010528405d18dc623086f06a7b52eb0ab3b4981cd5f487e77594871193d4b3fbd1021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ccc233af3c5b6565c129b7588e6db7f8f1fd8e6a313cf5b4b44cdba2574134c 0.600000000000 1594522 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": 1114675, "vin": [ { "gen": { "height": 1114665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ccc233af3c5b6565c129b7588e6db7f8f1fd8e6a313cf5b4b44cdba2574134c" } } ], "extra": [ 1, 5, 40, 64, 93, 24, 220, 98, 48, 134, 240, 106, 123, 82, 235, 10, 179, 180, 152, 28, 213, 244, 135, 231, 117, 148, 135, 17, 147, 212, 179, 251, 209, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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