Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4b87c4835498af05b4e124e9fd30e5d4bef6642588c67460f001f458e587b63

Tx prefix hash: c7218c8e49b37d2e53351ac69cdeec775d18ec41fbc59b2b1b228e0e4a204295
Tx public key: b7f8fd0c3e532fdf809341c5651abfc7dbdc11ffcdb8a045a8f4d57e6dae6772
Timestamp: 1727462437 Timestamp [UCT]: 2024-09-27 18:40:37 Age [y:d:h:m:s]: 00:230:13:53:10
Block: 1119419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164627 RingCT/type: yes/0
Extra: 01b7f8fd0c3e532fdf809341c5651abfc7dbdc11ffcdb8a045a8f4d57e6dae6772021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91f4d87457ac57e0e9a27fcdbd374a604e5d0b2361185d2846c43f574eb87b5 0.600000000000 1600970 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": 1119429, "vin": [ { "gen": { "height": 1119419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91f4d87457ac57e0e9a27fcdbd374a604e5d0b2361185d2846c43f574eb87b5" } } ], "extra": [ 1, 183, 248, 253, 12, 62, 83, 47, 223, 128, 147, 65, 197, 101, 26, 191, 199, 219, 220, 17, 255, 205, 184, 160, 69, 168, 244, 213, 126, 109, 174, 103, 114, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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