Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22b56a7e11bcd06cb47af3a23d1e940445af415a5a72a5a105174979418f4394

Tx prefix hash: 41cec7c51765eb0dca2c83a388d6885a9c43346c65047ceb19a4ad2553eae70d
Tx public key: 54c1a8e3776f3715b72c2f6eff818c8666a92a0450b3a1624f72aa54336baa08
Timestamp: 1702373064 Timestamp [UCT]: 2023-12-12 09:24:24 Age [y:d:h:m:s]: 01:137:14:38:54
Block: 911430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359498 RingCT/type: yes/0
Extra: 0154c1a8e3776f3715b72c2f6eff818c8666a92a0450b3a1624f72aa54336baa0802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bab2f1f146a3cec526408e782182519a112cfbf35aca4be62c1a516c474944d 0.600000000000 1368632 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": 911440, "vin": [ { "gen": { "height": 911430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bab2f1f146a3cec526408e782182519a112cfbf35aca4be62c1a516c474944d" } } ], "extra": [ 1, 84, 193, 168, 227, 119, 111, 55, 21, 183, 44, 47, 110, 255, 129, 140, 134, 102, 169, 42, 4, 80, 179, 161, 98, 79, 114, 170, 84, 51, 107, 170, 8, 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