Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b5f19c14e7fe2b6e8ddc78278ff4f5656139c83b0162bb9dfe3d1d647dcb1f

Tx prefix hash: 7f86534e5f734dc671ee70c78d2472f22d044ef5a1cea4d87d574c8d5a075e81
Tx public key: 66a0e2a02202da0e117a1403a6301309a5118063812e586cd052d1a7598eab01
Timestamp: 1673793293 Timestamp [UCT]: 2023-01-15 14:34:53 Age [y:d:h:m:s]: 02:014:09:27:02
Block: 675334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531937 RingCT/type: yes/0
Extra: 0166a0e2a02202da0e117a1403a6301309a5118063812e586cd052d1a7598eab01021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.550896901000 dcy

stealth address amount amount idx
00: 4bf9c3836beaeb0d511f23f7941a35c6ad9a893b85ff8246ed08346d147988af 3.550896901000 1117009 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": 675344, "vin": [ { "gen": { "height": 675334 } } ], "vout": [ { "amount": 3550896901, "target": { "key": "4bf9c3836beaeb0d511f23f7941a35c6ad9a893b85ff8246ed08346d147988af" } } ], "extra": [ 1, 102, 160, 226, 160, 34, 2, 218, 14, 17, 122, 20, 3, 166, 48, 19, 9, 165, 17, 128, 99, 129, 46, 88, 108, 208, 82, 209, 167, 89, 142, 171, 1, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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