Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9682f898624e0fe977c1acb5850e6e414be07a1d937b8432de2c1227231c2e

Tx prefix hash: e82faa54c432881557160d85ea945eb11ecfd218e8ac1f3a85242c32a1ab46b8
Tx public key: bb04a51bec500a3676c2839af9f8758692350c12064118c8d6df4ab057410071
Timestamp: 1698542157 Timestamp [UCT]: 2023-10-29 01:15:57 Age [y:d:h:m:s]: 01:199:15:22:34
Block: 879871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403702 RingCT/type: yes/0
Extra: 01bb04a51bec500a3676c2839af9f8758692350c12064118c8d6df4ab057410071021100000004faf35c9c000000000000000000

1 output(s) for total of 0.745799586000 dcy

stealth address amount amount idx
00: 0c4eb0c9748e580179f91f84ccb601b1c3dc991cf9aafd26838dca8e1f6ea214 0.745799586000 1335411 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": 879881, "vin": [ { "gen": { "height": 879871 } } ], "vout": [ { "amount": 745799586, "target": { "key": "0c4eb0c9748e580179f91f84ccb601b1c3dc991cf9aafd26838dca8e1f6ea214" } } ], "extra": [ 1, 187, 4, 165, 27, 236, 80, 10, 54, 118, 194, 131, 154, 249, 248, 117, 134, 146, 53, 12, 18, 6, 65, 24, 200, 214, 223, 74, 176, 87, 65, 0, 113, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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