Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce3dad44c7f84c93b13faf17661098ea7b7c157f5bdd80530f11c59f3a69ed7

Tx prefix hash: 4920ea3fade82ad8cfb86be947e978305122dfa6a7ec759c119e4c08daa93a4a
Tx public key: 6923a0d67d49bdcd3b0f06b6445cd6ecad7739b9a9f6fc34a8225374bb7079a1
Timestamp: 1702424679 Timestamp [UCT]: 2023-12-12 23:44:39 Age [y:d:h:m:s]: 01:155:04:24:28
Block: 911867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372045 RingCT/type: yes/0
Extra: 016923a0d67d49bdcd3b0f06b6445cd6ecad7739b9a9f6fc34a8225374bb7079a102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecbc4289510dc90ca2aa3553cd1b08f5071b778eeb19db9f74e907d13e623eba 0.600000000000 1369083 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": 911877, "vin": [ { "gen": { "height": 911867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecbc4289510dc90ca2aa3553cd1b08f5071b778eeb19db9f74e907d13e623eba" } } ], "extra": [ 1, 105, 35, 160, 214, 125, 73, 189, 205, 59, 15, 6, 182, 68, 92, 214, 236, 173, 119, 57, 185, 169, 246, 252, 52, 168, 34, 83, 116, 187, 112, 121, 161, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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