Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d614bf983c9c742d6c245104776d8a2632886a2604eac8f5e5864cf586d9d679

Tx prefix hash: 1b075e30dde89e826c303f821de046447c04145dfe17776ef6e1551d81d966c1
Tx public key: 8a71d59c486902e4ea2fdcb370e0824b222f2e63af94463f28b7832bea4925e1
Timestamp: 1716106043 Timestamp [UCT]: 2024-05-19 08:07:23 Age [y:d:h:m:s]: 00:248:18:18:16
Block: 1025283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177980 RingCT/type: yes/0
Extra: 018a71d59c486902e4ea2fdcb370e0824b222f2e63af94463f28b7832bea4925e10211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a4734e3d29c7a64d5e833d06b09f65949c966f2914225eb037f5d3e87bdd3d 0.600000000000 1491674 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": 1025293, "vin": [ { "gen": { "height": 1025283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a4734e3d29c7a64d5e833d06b09f65949c966f2914225eb037f5d3e87bdd3d" } } ], "extra": [ 1, 138, 113, 213, 156, 72, 105, 2, 228, 234, 47, 220, 179, 112, 224, 130, 75, 34, 47, 46, 99, 175, 148, 70, 63, 40, 183, 131, 43, 234, 73, 37, 225, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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