Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8acea0f2d910c8d714031e66a34c5c759b038cb8f24239c63a2992cf59753175

Tx prefix hash: f0495e99c83b5346eadd127a6d008985e81e3c42cd89c5ac18296a4932a0daef
Tx public key: 6a19c310d18cd728b1b1e6f896b49939b466ddd042490fd8a3b45b1839803556
Timestamp: 1696113876 Timestamp [UCT]: 2023-09-30 22:44:36 Age [y:d:h:m:s]: 01:190:07:51:29
Block: 859727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397068 RingCT/type: yes/0
Extra: 016a19c310d18cd728b1b1e6f896b49939b466ddd042490fd8a3b45b183980355602110000000133af99f4000000000000000000

1 output(s) for total of 0.869696259000 dcy

stealth address amount amount idx
00: effbc8593554d33a379ec6e3114ffdcdbe0ba96f14a5ccdd249912d1983eadbd 0.869696259000 1313969 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": 859737, "vin": [ { "gen": { "height": 859727 } } ], "vout": [ { "amount": 869696259, "target": { "key": "effbc8593554d33a379ec6e3114ffdcdbe0ba96f14a5ccdd249912d1983eadbd" } } ], "extra": [ 1, 106, 25, 195, 16, 209, 140, 215, 40, 177, 177, 230, 248, 150, 180, 153, 57, 180, 102, 221, 208, 66, 73, 15, 216, 163, 180, 91, 24, 57, 128, 53, 86, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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