Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6093f41b397b7bf245cb3f1b2731622efb51286170ed95699559a762b654b414

Tx prefix hash: 428df129d3e8b8acac417f0c9d5e5a48d30985046518ae80cc55e6d4051eb116
Tx public key: 1501996148ad68fd606a512f5eb1e0c3d7c442b98a6985d8b004a5a2545b671e
Timestamp: 1734079621 Timestamp [UCT]: 2024-12-13 08:47:01 Age [y:d:h:m:s]: 00:096:02:55:18
Block: 1174197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68480 RingCT/type: yes/0
Extra: 011501996148ad68fd606a512f5eb1e0c3d7c442b98a6985d8b004a5a2545b671e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96ba555f02c605c805ab8c8480c631d9334d135d007fcb1c4c799e2e2d649b2f 0.600000000000 1660318 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": 1174207, "vin": [ { "gen": { "height": 1174197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96ba555f02c605c805ab8c8480c631d9334d135d007fcb1c4c799e2e2d649b2f" } } ], "extra": [ 1, 21, 1, 153, 97, 72, 173, 104, 253, 96, 106, 81, 47, 94, 177, 224, 195, 215, 196, 66, 185, 138, 105, 133, 216, 176, 4, 165, 162, 84, 91, 103, 30, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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