Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be46321fbf428078dbdb1ce905329421c67f85636cb9ba9a1e08382d59994f3c

Tx prefix hash: d8ba0ee252ad9dee0681caae99243443ad5a1c6c9837f7781da58b2e8fa4ad0a
Tx public key: e247a478e3157ba3ae932ed77134ac11add0250bbb33b73f7672a5d418f32270
Timestamp: 1699416918 Timestamp [UCT]: 2023-11-08 04:15:18 Age [y:d:h:m:s]: 01:211:00:13:57
Block: 886915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412039 RingCT/type: yes/0
Extra: 01e247a478e3157ba3ae932ed77134ac11add0250bbb33b73f7672a5d418f3227002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.706777038000 dcy

stealth address amount amount idx
00: 5f67334fdaed4e67c90603e6c3ea2debc060db83a5e003e4cbb48587cd930738 0.706777038000 1342762 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": 886925, "vin": [ { "gen": { "height": 886915 } } ], "vout": [ { "amount": 706777038, "target": { "key": "5f67334fdaed4e67c90603e6c3ea2debc060db83a5e003e4cbb48587cd930738" } } ], "extra": [ 1, 226, 71, 164, 120, 227, 21, 123, 163, 174, 147, 46, 215, 113, 52, 172, 17, 173, 208, 37, 11, 187, 51, 183, 63, 118, 114, 165, 212, 24, 243, 34, 112, 2, 17, 0, 0, 0, 1, 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